|
![](/i/fill.gif) |
Christopher James Huff wrote:
>
> Xplo, you did not post a minimal scene...
Fine. By the strictest technical definition, it was not a minimal scene.
So what? Why should I care? Why should *you* care? The code had one and
only one purpose: to be pasted into POV-Ray and rendered so that the
resulting image can be observed. It fulfills this purpose, therefore
there's nothing wrong with it.
Should I apologize for not realizing that people here would be so anal
as to complain about a fifth of the content of 35 lines of code?
> you did not mention you were using an unofficial
> version, which *does* matter.
It would only matter if the bug only existed in the unofficial version.
Had that been the case, the number of people saying "huh? I don't see
this" would have shown it to be so, and it would still be valuable
information, given MegaPOV's popularity and the fact that patches tend
to find their way into official code.
For all I knew, the phenomenon had a perfectly valid explanation and
would not be considered a bug, in the same way that limits on magnitude
of scale have a perfectly valid explanation and are not considered a
bug.. which is why I phrased my initial post as a question ("what's
going on?") as opposed to a bug report ("found in version X, running
under OS Y on hardware Z").
> Warp made a simple suggestion...
He did?
"Argh! And why all the unneeded whitespace bloating the code?"
Could you please point out which part was the suggestion? All I see is
pointless bitching and criticism.
> and you
> responded with "Bite me, Warp.", which was entirely unexpected and
> unjustified.
I beg to differ with your analysis, sir. It was his criticism that was
entirely unexpected and unjustified. My response was perfectly natural.
I'm sorry to see that you're taking his side here. I would have expected
more from the "helpful POV community" than this.. especially given that
the question of whether this is a bug in POV-Ray apparently remains
unresolved.
(Then again, I can think of two other bugs in POV-Ray that have gone
unresolved for some time now, both of which cause crashes and one of
which is confirmed and documented. I guess I'd better learn C if I want
any hope of seeing them fixed.)
-Xplo
Post a reply to this message
|
![](/i/fill.gif) |